<p>The following configuration settings are available to administrative users on the <span id="roxconfiglink"><i>Configuration</i> page in your <i>ExportZen Studio</i>, which you can access via Site Settings / ExportZen Studio / Configuration Settings</span>.</p><p>Each setting has a global value scoped to the SharePoint server farm, and this value can optionally be overridden on the Site Collection level. The following settings are available:</p>
<h3>User Interface Language</h3>
<p>ExportZen has been localized for multiple languages. In addition to English and German, if you have added partial translations in other languages (via Site Settings / ExportZen Studio / DIY User Interface Localization), these languages will be available for selection here. Changing this setting affects all ExportZen user interfaces except captions and descriptions of Features, List Templates, Column Types, Content Types or Web Part Templates (those are always loaded directly by SharePoint based on the current Web Site locale).</p>
<p><strong>You can pick one of the following options</strong> on the <i>Configuration</i> page in the <i>ExportZen Studio</i>:</p>
<ul>
<li><i>(Like site, or English)</i></li>
<li><i>English</i></li>
<li><i>Deutsch</i></li>
<li><i>French</i></li>
</ul>
<h3>Hide (2007) or disable (2010) SharePoint&#39;s out-of-box &quot;Export to Excel&quot; command</h3>
<p>By default, your ExportZen action commands co-exist together with the built-in, out-of-box &#39;Export to Excel&#39; command. If you intend to fully replace that functionality with ExportZen, you can set whether and when to show (2007) / enable (2010) the built-in, out-of-box &#39;Export to Excel&#39; command (affects both both the SharePoint 2007 List Actions tool-bar menu item and the ribbon button in the SharePoint 2010 &#39;Connect and Export&#39; section of the List Tools ribbon tab).</p>
<p><strong>You can pick one of the following options</strong> on the <i>Configuration</i> page in the <i>ExportZen Studio</i>:</p>
<ul>
<li><i>Never</i></li>
<li><i>Only if CSV export actions exist (requires activated Site Collection feature)</i></li>
<li><i>Always (requires activated Site Collection feature)</i></li>
</ul>
<h3>Separator for exported multi-valued Column data</h3>
<p>This specifies the text used to combine the export value representations of List Columns containing multiple values, such as multi-Choice and multi-Lookup Columns.</p>
<p>After you have customized this setting, you can click the <b>Reset to Default Value</b> link on the <i>Configuration</i> page in the <i>ExportZen Studio</i> to restore the following default value:</p>
<pre>, </pre>
<h3>No default instances of ExportZen configurables on the Site Collection level (NOT recommended!)</h3>
<p>Configurables are lists of items for defining and customizing the behaviors of this software (such as Export Actions in ExportZen, Data Sources and Data Field Templates in PeopleZen, Print Views and Print Launchers in PrintZen, Upload Actions in UploadZen). By default, each Site Collection has its own non-removable default instance that can be customized and to which additional instances can be added. In extensive farm setups (1000s of Site Collections), these default instances may be a hindrance and using only custom farm-level instances may be preferable. Tick this option to never provide the default instance on the Site Collection level.</p>
<h3>By default, no inclusion of jQuery library v1.6.1 (NOT recommended)</h3>
<p>Some ExportZen end user-facing artifacts require (and load into the respective host pages) the jQuery library, version 1.6.1. Embedding jQuery more than once in a single page can cause JavaScript warnings in Internet Explorer with <i>some few</i> jQuery plugins (and only if any are used in your farm at all). On the <i>Configuration</i> page in the <i>ExportZen Studio</i>, tick this check box <i>only</i> if your master pages, web pages or third-party extensions also already include jQuery globally (not just on some individual pages) and independently of ExportZen to prevent ExportZen from loading jQuery too. If you do so, you need to make sure jQuery 1.6.1 or higher is loaded on each page hosting also hosting ExportZen user interface artifacts, or ExportZen will appear broken. This is a global default setting that can be optionally overridden locally where applicable.</p>
